This PR adds BladeFormatter.

Review for BladeFormatter master-055137b-2026.05.30.08.24.01

• Repository is at https://github.com/RushabhJoshi/BladeFormatter
• Latest version 1.0.0 is 1 commit behind tip of master.

3 failures:

• The binding ['ctrl+alt+f'] has no context. Packages should only ship key bindings that use a specific context such as 'selector', 'setting.*', or a custom context key. If the binding defines a main entry-point to your package, move it to an example keymap instead so users can decide on their own.
  File: Default (Windows).sublime-keymap
• The binding ['ctrl+alt+f'] has no context. Packages should only ship key bindings that use a specific context such as 'selector', 'setting.*', or a custom context key. If the binding defines a main entry-point to your package, move it to an example keymap instead so users can decide on their own.
  File: Default (Linux).sublime-keymap
• Invalid modifier key 'cmd'
  File: Default (OSX).sublime-keymap
  Binding: {"command": "blade_format", "keys": ["cmd+alt+f"]}

5 warnings:

• subprocess.Popen is used in a Windows-supported package without hidden-window handling. Pass startupinfo with STARTF_USESHOWWINDOW/SW_HIDE, or use CREATE_NO_WINDOW, to avoid flashing console windows.
  File: BladeFormatter.py
  Line: 130, Column: 23
• The package does not contain a top-level LICENSE file. A license helps users to contribute to the package.
• Package defines '.sublime-settings' files but is missing 'Default.sublime-commands' to add a Command Palette entry to edit them.
• 'Main.sublime-menu' has no 'Package Settings' entry for 'BladeFormatter'
• 'Main.sublime-menu' has no settings entry under 'Preferences > Package Settings > BladeFormatter' to edit 'BladeFormatter.sublime-settings'. Add a 'Settings' entry using edit_settings with 'args.base_file' set to '${packages}/BladeFormatter/BladeFormatter.sublime-settings'.

• Your package is not sorted correctly.
• "as they are standard, highly expected shortcuts for formatters" ... All the more reason not to claim them ;) especially not without any context (e.g. what syntax/language you're in) checks. Just don't ship with keybindings, and have a look at our docs for ways of allowing users to easily set up their own.
• Your package is using the ancient open_file method for settings, instead use edit_settings like you do in the sublime-commands file.

It looks like https://packages.sublimetext.io/packages/Formatter can also format Blade, and https://packages.sublimetext.io/packages/Fmt might also be able to do it. What does your package bring to the table that can't be contributed to either of those?